collection

2.2. Consuming time zones

Quite often, applications have a list of time zones stored internally or in a non-standard registry, and when a meeting is created with a time zone, the application will:

  1. Try to match the supplied time zone with its internal representation. This match can be accomplished by using any of these techniques:

    • Have an algorithm pick an internal time zone with the closest corresponding set of rules to the supplied one.

    • Try to match the TZID with its internal counterpart.

  2. If no match can be found the application will do one of these:

    • Return an error.

    • Add the new time zone to its internal time zone list.

At this point, these problems can occur: